home *** CD-ROM | disk | FTP | other *** search
- Path: bcarh8ab.bnr.ca!hwt
- From: hwt@bnr.ca (Henry Troup)
- Newsgroups: comp.lang.c
- Subject: Re: Secure from Decompiling??
- Date: 30 Jan 1996 17:39:40 GMT
- Organization: Bell-Northern Research Ltd., Ottawa, Canada
- Message-ID: <4ell4s$evt@bcarh8ab.bnr.ca>
- References: <4djaq2$jd5@earth.superlink.net> <4eirrd$dir@crl.crl.com>
- Reply-To: hwt@bnr.ca
- NNTP-Posting-Host: bcarhd7b.bnr.ca
-
- >rstewart@mars.superlink.net (Bob Stewart) writes:
- >
- >> I have a compiled C program containing a string that I want no one to
- >>be able to see, even with a decompiler.
-
- You can stop simple attacks, but there are no general solutions.
- What you are describing is "security through obscurity" - generally
- not the best way.
-
- Depending on the applications, public key/trap doors or zero-knowledge
- proofs may be what you want - see sci.crypt, I think.
- --
- Henry Troup - hwt@bnr.ca (Canada) - BNR is not committed to anything I say
- Leap years are years where the year number is a multiple of four with the
- exception: If a year is a multiple of 100, then it is only a leap year if it
- is also a multiple of 400. For example, 1900 was not a leap year, but 2000 is.
-